fix: Allow host-header-allowlist to be set in configuration file #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables users to be able to define the
host-header-allowlistin the configuration file. At the moment, if you attempt to set these values in the configuration file, they are not propagated to the variables used in the middleware due to how viper's marshaling works.I would also propose that we remove the
enable-host-header-allowlistflag from the configuration entirely as we can infer that this is what the user wants to do ifhost-header-allowlistconfigured. It can be a little confusing to define the list, but not have it actually take effect.